Post not yet marked as solved
Often things take longer than you think. Do it right.
Post not yet marked as solved
This watch, now devoid of developer profiles, and running standard released 7.5, with no profiles what so ever, when trying to upgrade to 7.6 ( released yesterday), .....
... behaves identically. It throws the error Unable to Verify Update. The watchOS update couldn't be verified because you are not connected to the Internet.
Still stuck in 7.5, although the world has moved on to 7.6
Post not yet marked as solved
Factory reset, retry - same problem. I'm gonna have to learn to love watchOS 7.5
I am wondering, watchOS 8 is billed as "always on", a feature introduced in Series 5 watches. My watch is a Series 4, and is not normally "always on". I was wondering about the battery drain of the beta. Perhaps I am spared the experience of watchOS 8 betas, due to old hardware.
Does anyone know if watchOS 8 runs on "not always on" hardware like my Series 4?
Post not yet marked as solved
Un-pair, re-pair, set up as new - same problem
Post not yet marked as solved
Read the Friendly Manual!
from release notes for 12.4: Known Issues
Xcode may hang if the host Mac is connected to an iOS device which has one or more companion watches. The hangs occur when the watches aren't fully prepared for development, or if they are experiencing poor wireless connectivity. (72490921) (FB8945320)
Workaround: Power off the watches, or unpair them from the iPhone.
You can force Xcode to freshly prepare a watch for development using these steps:
Post not yet marked as solved
I am seeing this on a Series 6 Watch, no more beta. Watch was fine until I did the 7.0.2 upgrade. Now it drains very fast, a percent every minute or two, and must be charged 3 times a day, and doesn't make it through the night.
Post not yet marked as solved
If <key>CFBundleDisplayName</key>
has a <string>Dog Disc & Wind</string>
which contains an & ....
The info.plist file fails to open in Xcode with error: Failed to open property list: Encountered unknown ampersand-escape sequence
Workaround: edit the info.plist with TextEdit to remove the &
